			-----------------------------------			
			MSCMS 2001 Release Note - Readme File
				     June 2001
			-----------------------------------
                (c)Microsoft Corporation. 2001. All rights reserved.


How to Use This Document
========================                                                       

To view the Readme file on-screen in Windows Notepad, maximize the Notepad 
Window. In the Edit menu, click Word Wrap. To print the Readme file, open it in
Notepad or another word processor and then use the Print command on the File menu.

Viewing the User Documentation
==============================

The customer user information is on the CD in the form of PDFs. You need to use the Adobe Acrobat Reader 4.0 or later to view the documentation suite. Download a copy at www.adobe.com.

Summary
=======

This Readme file contains important information about the Microsoft Content Management Server 2001. Refer to the manuals for full details on setting up the MSCMS 2001 and using the MSCMS 2001 Site Builder and MSCMS 2001 Web Author.

Contents
========

This Readme file contains the following information.

Software and Hardware Requirements
Configuration Issues
KNown Issues:
	Installation 
	MSCMS 2001 Server
	MSCMS 2001 Site Builder
	MSCMS 2001 Web Author
	MSCMS 2001 Publishing API
	MSCMS 2001 Site Stager
	MSCMS 2001 Content Connector for Commerce Server 2000
	MSCMS 2001 Site Deployment Manager
	Multilingual Support

Software and Hardware Requirements
==================================

Refer to the MSCMS 2001 Setup Guide for complete configuration information about the MSCMS 2001. Then, for further information on managing an MSCMS 2001 Web site, refer to the MSCMS 2001 Site Administrator's Guide.


Configuration Issues
====================

Many of the configuration issues involve the MSCMS 2001 Web Author file structure. 

A. MSCMS 2001 Web Author directory structure

The MSCMS 2001 Web Author ASP files are organized into three main directories:

*  /NR/System/WBC/Customizable
*  /NR/System/WBC/Internals
*  /NR/System/WBC/SiteInterface

Refer to Chapter 8, "Working from the Sample Web Author" in the MSCMS 2001 Site Programmer's Guide, on this CD, for complete information about the directories and their contents.

B. Read-only access must be granted to Everybody

You need to grant read-only access to Everybody for all directories and files that you have created for your Web site. 

C.  Database verification

A database scan is done by the InstallShield Wizard before beginning an upgrade. 


Known Issues
============

Following are the known issues for this release of MSCMS 2001, categorized by the process or component in which they can occur.

INSTALLATION


Users can log on using account from an unsupported Windows NT domain
--------------------------------------------------------------------

When you remove supported NT domains, Site Server organizational units (OUs), or Active Directory service containers, MSCMS 2001 does not go through the database and remove all users from these domains/OUs/containers. The result is that users can still log on and are still displayed in the MSCMS 2001 Site Builder. If you don't want these users to be able to log on, you must explicitly delete them.

SCA and LDAP services
----------------------

If you run the Server Configuration Application (SCA) and choose not to use LDAP services, LDAP users can still log on the MSCMS 2001 Site Builder as LDAP users. You need to manually remove LDAP users from the database that uses Site Builder.


MSCMS 2001 SERVER

Configuration of Active Directory users in MSCMS 2001 rights group
-----------------------------------------------------

We strongly recommend that you not mix Windows 2000 and Active Directory servers LDAP domains. For AD users, always use the User Principal Name (UPN) or the distinguished name (DN) to log on. If you are migrating your existing NT users, the first time they log in, they should do so as NT users.


MSCMS 2001 SITE BUILDER

Declined postings in Site Builder and Web Author
------------------------------------------------

On both the Site Builder and Web Author, the following behavior is exhibited in the 
workflow:

Declined postings stay in the declined state after changes have been made to the page. Typically, the following sequence of tasks would have been followed: Log on as an author, create a page and a posting, and submit the page. Then log in as an editor and approve the page. Log in as a moderator and decline the posting. Log back in as an author, modify the page and resubmit. Finally, log back in as an editor and re-approve the page. 

However, when you log back in as a moderator, the status of the posting is still declined, and there is no indication that the page has changed since it was declined. Because moderators don't have permissions to do revision history, they do not know if the author has made a change.

Need to add space between images
--------------------------------

When creating a page based on a template that has a multipurpose placeholder and you want to add several images to the placeholder, be sure to add space between them or their individual links will be incorrect when you save the page.

Network environment and IP changing
-----------------------------------

The Site Builder doesn't work in a network environment where the IP gets changed in mid-session, for example, by proxy servers.

Copying folder with several pages
---------------------------------

When you try to copy a folder with several pages (for example, over 100), the message Cant find the requested item appears in the progress box. However, the folder and pages are actually properly copied. If you try to copy an extremely large folder (for example, over 1000 pages), your copy operation may suspend itself and you will receive an Internet Explorer message, indicating your action is canceled.

Toolbar buttons dont work
--------------------------

When in the MSCMS main window, toolbar buttons may occasionally stop functioning when working with listview items. If this occurs, restart the Site Builder, or use the main menu or the user context (right-click) menu.

Disabling hyperlinks in placeholders
------------------------------------

Template designers can disable the Add Hyperlinks property for a placeholder so authors cannot add hyperlinks in the placeholder using the Insert>Hyperlink menu commands. Authors can however, type URLs directly into the placeholder and they will function as hyperlinks. Because the Add Hyperlinks property is disabled, hyperlinks entered in this way cannot be modified using the Edit Hyperlink command.

Resizing images in a placeholder
-------------------------------- 

When editing the placeholders HTML in the Template Design window, you cannot adjust the images height and width attributes by a percentage. For example, the following tag will not work correctly: 
	<img src="Image_Name" width =100%"> 
However, you can change the image size by entering a numerical value (non-percentage) in the width or height attribute of the image.

Copying hyperlinked images
-------------------------- 

When using Site Builder, if you copy an image that contains a hyperlink from Internet Explorer, the hyperlink is not copied into the placeholder.

Canceling modifications to placeholder properties
--------------------------------------------------

When selections are made in the Placeholder Properties dialog box, switching to one of the other tabs causes the changes made on the previous tab to be committed. Selecting Cancel will not undo the changes made to properties on the tab after switching to another tab.

Previewing pages that use multiple views on sites using Site Server
-------------------------------------------------------------------

When previewing a page that uses multiple views on a Site Server, sometimes the user authentication dialog box will appear. To view the page, the user can enter their name and password in the authentication screen, or click the preview button again. A preview of the page opens in a Web browser.

Attachments
----------- 

If a template designer sets the properties of a placeholder to allow attachments and later removes that permission, in some cases attachments will not be removed from pages that use that template when the page is edited. For example, attachments will not be removed from placeholders that no longer allow attachments, but allow hyperlinks. This is because both attachments and hyperlinks use the <A HREF> tag. 

Microsoft Word 2000 text formatting
-----------------------------------

Microsoft Word 2000 style sheets are not copied over when users paste text into a placeholder. The workaround is to set the template to use the same styles as those used in the Word 2000 document.

Internal time settings out of sync
----------------------------------

You may notice when publishing from the Site Builder that pages you post to start immediately do not do so. This is because your MSCMS 2001 server and Site Builder may be out of sync in their internal time settings.

Adding local group to domain controller
---------------------------------------

When in the User Roles container, if you add a local group for the MSCMS 2001 servers domain controller (DC), and then try to log on, the login operation fails.

Copy and paste image from HTML file converted from RTF
------------------------------------------------------

When editing pages and templates, you cannot copy and paste an image from an HTML file that was converted from a rich text format (RTF) file. The workaround is to paste directly from Word 2000 to the placeholder rather than saving the Word 2000 document as HTML and then pasting it into the placeholder. 

Set owner for imported objects shows up as <unknown>
------------------------------------------------------

The type of users under set owner for imported objects panel may show up as <Unknown>. It should say either NT or LDAP user.

Macromedia Dreamweaver 3 and 4
------------------------------ 

You cannot drag-and-drop a placeholder into a new template with Macromedia Dreamweaver versions 3 or 4 as the HTML editor. Note that the copy-and-paste function still works from the template Design Palette (as do previous versions of Dreamweaver). With Dreamweaver 4, you must be in a non-WYSIWYG text view in order to do the copy-and-paste function.


MSCMS 2001 WEB AUTHOR

Declined postings stay in the declined state
-------------------------------------------- 

Note the explanation of this behaviour under the Site Builder issues section.

Display name contains double quotation marks
--------------------------------------------

If the display name of a channel contains double quotation marks (), you will get a JavaScript error when you switch to edit mode and open the copy page or move page dialog boxes.


Replacing item with renamed item
--------------------------------

If you replace an item with the same item but that has been renamed on the desktop, the replacement operation will fail. Consider installing Microsoft Office on your system to get around this.

Access to the default page
--------------------------

Under IIS 5, you cant access the default page in your site if the page name contains an apostrophe (for example, Whats New). To work around this problem, use the ServerSideRedirect method to redirect the URL without encoding it.

Revision history doesnt show insert color for new table
--------------------------------------------------------

When doing a comparison of two newly created tables in a page, the content is marked as inserted. However, there is no insert color showing the differences between the two tables.

Naming inconsistency between Site Builder and Web Author
--------------------------------------------------------

There is an inconsistency in the way postings, channels, and resources are displayed in the Site Builder (by Name) and the Web Author (by Display Name).

Multipurpose placeholders and tags being removed
------------------------------------------------

When using the <script> and <object> tags in multipurpose placeholders that have been enabled for HTML source editing, be aware that the Web Author removes these tags and everything in between.

Placeholder issue
-----------------

When a placeholder in the Web Author is set to allow movie files, and a .MOV file is added (using the <EMBED> tag), the video size is very small. We strongly recommend that users not link or embed videos.


MSCMS 2001 PUBLISHING API

Publishing API Searches.GetByURL method returns null values
----------------------------------------------------------- 

In some circumstances, searching for a posting by the value of its URL will return a null value. We recommend using the Searches.GetByPath method instead.

LastApprovedDeclinedBy method
-----------------------------

The LastApprovedDeclinedBy method occasionally returns the wrong user.

Channel.CreateConnectedPosting method
-------------------------------------

The definition for the two properties, CreatedBy and CreatedDate should read: CreatedBy is the user who created the underlying page. CreatedDate is the date and time the underlying page was created.

Commit and Rollback methods deprecated/removed for Channel, Posting, and Resource
---------------------------------------------------------------------------------

The Autosession.CommitAll method is the only one that should be used to commit data to a database. In addition, Autosession.RollbackAll should be the only method you use to undo all MSCMS 2001 Publishing API objects that have been modified in the current session transaction. 


MSCMS 2001 SITE STAGER

Site Stager and posting names
-----------------------------

MSCMS 2001 Site Stager wont stage two postings with the same name in the same channel. MSCMS 2001 is 
case-sensitive for file names in Preview mode, but when files are staged, the name is lowercase.

Secure Socket Layer (SSL) and Site Stager
-----------------------------------------

MSCMS 2001 Site Stager does not operate on sites that use SSL.

Site Stager redirection 

If you use Response.Redirect to redirect browsers, the URL to which you are redirecting should not be a relative URL. Rather, it should use a full path, such as /files/recent/headline.html. Redirecting to relative URLs will lock the Site Stager in an infinite loop. 

If redirecting to URLs returned by MSCMS 2001 properties, such as Posting.URL, you must manually modify the URL before redirecting to it. This is necessary because in the Staging Autosession mode, MSCMS 2001 wraps staging tags (<NCOMPASSSTAGINGSERVER>...</NCOMPASSSTAGINGSERVER>) around all URLs it generates. The files included with the MSCMS 2001 server include a VBScript function to strip off staging tags. The StripOffStagingTags function in the Server/httpexec/shared/TemplateSwitching.inc file can be used to make generated URLs compatible with redirects. The following example shows how this is done.

'=================================================================

' Removes <NCOMPASSSTAGINGSERVER> tags from urls. These tags appear

' in staging mode. This function is most commonly used to remove

' staging tags from redirection URLs in Staging mode.


' (this function is from the intranet_common.inc file)

Function StripOffStagingTags(strUrl)

	StripOffStagingTags = Replace(Replace(strUrl, "<NCOMPASSSTAGINGSERVER>", ""), "</
NCOMPASSSTAGINGSERVER>", "")

End Function


' check mode - if Autosession.IsModeStaging is true, you must 

' modify header response redirects in the following manner:

If Autosession.IsModeStaging Then

	Dim pPosting

	Dim strURLWithStagingTags

	Dim strURLNoStagingTags


	' set pPosting to the posting you want to redirect to 

	' ...


	' get URL - in Autosession staging mode, generated

	' URLs are wrapped in staging tags

	strURLWithStagingTags = pPosting.URL


	strURLNoStagingTags = StripOffStagingTags(strURLWithStagingTags)


	' redirect to cleaned-up URL

	Call Response.Redirect(strURLNoStagingTags)

End If


Cannot stage as LDAP user
-------------------------

Note there is a Site Stager limitation whereby you cannot stage a site as an LDAP user.


CONTENT CONNECTOR FOR COMMERCE SERVER 2000

Upgrading with a customized Content Connector solution site installed
---------------------------------------------------------------------

If you installed the previous version of MSCMS 2001 with Content Connector and created a customized connector site based on our MethodSystems.pup, you need to do the following steps.

1. Upgrade MSCSM 2001 server and Site Builder.

2. Immediately after the upgrade, run the SimulateUnpack.bat file in the commerce site application directory. This will recreate certain required virtual directory mappings. Refer to the MSCMS 2001 Setup Guide, Chapter7, "Installing Content Connector."

3. After running the batch file, back up the WBC_Customizable directory under your commerce site application directory and then replace its contents with those on the MSCMS 2001 installation CD in the following location: \InetPub\wwwroot\MethodSystems\WBC_Customizable. Any changes made to your version on the WBC_Customizable files can be merged into this set of files again.

4. In the Internet Information Server MMC, ensure that certain connector virtual directories point to the correct install path after the upgrade. In some circumstances, they may refer to their locations before upgrade. Verify that these virtual directories point to the correct path in the upgraded installation:

 /NR/ContentConnector/                    <InstallDir>\IIS_NR\ContentConnector
 /NR/ContentConnector/CS2000              <InstallDir>\IIS_NR\ContentConnector\CS2000
/NR/ContentConnector/CS2000/Framework     <InstallDir>\IIS_NR\ContentConnector\CS2000\Framework

5. Upgrade Content Connector.

6. We recommend you completely delete your existing BizDesk from the Commerce Server Manager, IIS, and the files in the directory. After deleting, use the new MethodSystems.pup file to add the new MethodSystemsBizDesk application back into your site. The PUP file is installed by default under \Program Files\Microsoft Content Management Server\ContentConnector\CS2000\SitePackage\.

There are other changes in the solution site code that may be beneficial to you. Review the files under \InetPub\wwwroot\MethodSystems to see if there are further changes that can be incorporated into your own solution site.


Page Profile Connection string is not correct
---------------------------------------------

Certain PCO operations incorrectly use the data connection string for campaigns to retrieve page profile or PCO information so you cannot put the profiles or PCO data on a different SQL Server machine than the campaigns. The workaround for this is to ensure the page profile and PCO tables are in the same database as the campaigns. 


PCOs don't show same product information as in the custom catalog  
-----------------------------------------------------------------
When a rich product posting is returned from a personalized content object (PCO), the content information shown by the default is always from the base catalog and never from any custom catalog, regardless of the currnt user's catalog sets.    


MSCMS 2001 SITE DEPLOYMENT MANAGER

Progress indicator doesn't work on some machines
------------------------------------------------

When doing an export or import operation (such as deep-copy) that uses the server-side progress indicator, you dont necessarily get a progress indicator. Check your IIS settings to see whether the ASP server-side script debugging is turned on. If so, turning it off should allow the progress indicator to work correctly. 

Export issue
------------

When exporting a file with very low Site Builder disk space, an Object Package (.rop) file with a size of zero will be created. Free up some disk space and try the export again.

Import issues
-------------

On the Import Preview, you may see duplicate objects listed under the Destination Objects that will be Deleted on Import section of the report.


MULTILINGUAL SUPPORT

Saving channel properties
-------------------------

Certain languages have more than one possible character set defined (for example, Japanese has Shift_JIS, EUC-JP, and so on). The Site Builder Authoring Tool and Properties dialog box supports multilingual content entry (for example, Display Name, Description, Custom properties) only for the most common character set of that language. For example, with Japanese, the Shift_JIS character set supported, but not the EUC-JP character set.

Multilingual fonts and character sets
-------------------------------------

As noted in the MSCMS 2001 Page Template Designer's Guide (Chapter 2), with the Site Builder operating on a Windows 2000 platform, you are able to use multilingual fonts and characters sets, but you must be using the operating system language of the Site Builder (for example, Japanese on a Japanese Windows 2000 operating system).

Language pack installation and CodePage directive
-------------------------------------------------

For any CodePage other than the system default to work under IIS, the corresponding language pack must be installed on the IIS server machine. Refer to the MSCMS 2001 Page Template Designer's Guide (Chapter 2) for instructions on language pack installation.

HTML source editing and multilingual text
-----------------------------------------

MSCMS 2001 Site Builder HTML source editing does not support multilingual text. When you open a multilingual page for authoring in the Site Builder and select Edit Source for a placeholder, the multilingual text appears garbled in the Edit Source dialog. The workaround is to edit the HTML source on a machine that is running the same operating system as the language you are entering (for example, edit Japanese HTML source only on a machine running a Japanese operating system).

Office 2000 on Japanese platforms
--------------------------------- 

When editing placeholder content with the Site Builder on machines with Office 2000, and Japanese versions of Windows, some formatting styles do not work properly. Applying heading styles, for example, will add heading elements to the selected placeholder text, but the appearance of the text does not change. This problem affects both Japanese and English text.

Copying non-English content
---------------------------

When copying non-English content (for example, Japanese) with formatting to a placeholder with no formatting allowed, content appears garbled. The workaround is to enable formatting in the placeholder.


Other issues 
============

Microsoft Office resource can't be replaced by item of the same type
--------------------------------------------------------------------

When you log on MSCMS 2001 as a resource manager and try to replace a Microsoft Office resource item of the same type (extensions, xls, doc, mdb, ppt, and rtf), the resource wont be replaced due to a problem with the registry settings. To have the resource properly replaced, consider installing Microsoft Office on your system.

Expiry date for postings and daylight savings time
-------------------------------------------------- 

If a posting is set to expire the day that daylight savings time begins (first Sunday in April) for the following year, the one-hour difference will not be taken into account. The solution is to add an hour to the time that the posting is due to expire.

Multiple-users 
--------------

If more than one MSCMS 2001 administrator is working on a site at the same time, care must be taken to coordinate tasks to avoid working on the same containers. 







